-
Notifications
You must be signed in to change notification settings - Fork 954
Update viber module #9730
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update viber module #9730
Conversation
|
Hi @itrujnara! Since you approved another PR I published earlier (#9727) which is really similar to this one, I suggested you as the reviewer. If you are available, thanks! |
SPPearce
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do you NOT want to fit the model in parallel?
|
Hi @SPPearce! Parallelisation is implemented via the external R package Since the module processes only one patient at a time, the runtime is relatively short (on the order of minutes), we are assigning the process_single label, which requests a single CPU and we believe it is safer to disable internal parallelisation in order to avoid potential cluster-specific issues. Let me know what you think about it, thanks! |
PR checklist
Closes #9724
The PR changes avoids fitting the tool in parallel.
topic: versions- See version_topicslabelnf-core modules test <MODULE> --profile dockernf-core modules test <MODULE> --profile singularitynf-core modules test <MODULE> --profile condanf-core subworkflows test <SUBWORKFLOW> --profile dockernf-core subworkflows test <SUBWORKFLOW> --profile singularitynf-core subworkflows test <SUBWORKFLOW> --profile conda